Cream of the Crop 12

home *** CD-ROM | disk | FTP | other *** search

/ Cream of the Crop 12 / Cream of the Crop 12 (Part II) / Cream of the Crop 12 (Part II).iso / OS2 / MAGUUCP3.ZIP / MAGUUCP.DOC < prev next >

Wrap

Text File | 1996-03-12 | 75.9 KB | 2,496 lines

MAGUUCP Communications Program for OS/2 Version 3.00C & 3.00D (formerly MAGCOM) (C)Copyright Gilmore Systems - 1989,1996 All Rights Reserved Voice: (818) 782-1870 FAX: (818) 782-2093 BBS: (818) 782-6290 Email: postmaster@gilmore.com Gilmore Systems 7354 Rubio Av. Van Nuys, CA 91406 U.S.A. Program by Chuck Gilmore MAGUUCP Communications Program for OS/2 Page 1 Introduction MAGUUCP is a companion communications program to Magnum BBS software for OS/2 from Gilmore Systems. MAGUUCP is an optional terminal & UUCP program sold separately (it is NOT included with Magnum BBS software). MAGUUCP offers standard terminal program features (ANSI, TTY, Xmodem [3 flavors], Ymodem [2 flavors], Zmodem). Additionally, it acts as the uucico interface between Magnum BBS (v8.08 & above) and an Internet Service Provider so that your Magnum BBS system can utilize Internet E-mail (with Domain Name Service from an Internet Service Provider). Although Magnum BBS software for OS/2 is not a requirement for running MAGUUCP, those who take advantage of the combination of MAGUUCP and Magnum BBS will be able to use Internet E-mail (messages on the BBS with 'attached files' are automatically uu-encoded into the outgoing message; incoming messages containing uu-encoded files are automatically uu-decoded and presented as an 'attached file' on the BBS). Additionally, LISTSERV functions are included with this combination (ie: send a message to a certain address on a Magnum BBS [ie: info@gilmore.com]) and an automatic response message will be sent. Alias names are also supported. MAGUUCP is a solid communications program for OS/2 which supports most of the modem handling features that other packages leave out such as CTS flow control (hardware handshake), DTE speeds higher than DCE (up to 115,200 baud), support for redirected serial ports on LAN's, Zmodem, Ymodem-G, Auto-Zmodem detect, Zmodem crash recovery, a powerful scripting language, etc. Although a fullscreen text application, you may also run it as a windowed text application. The programs comprising MAGUUCP are: MAGUUCP.EXE, ULFILE.EXE and DLFILE.EXE, 3 programs in all. ULFILE.EXE and DLFILE.EXE are called by MAGUUCP.EXE when you choose to upload or download files, meaning they don't use any memory unless file transfers are in progress. This frees up memory upon completion of file transfers. MAGUUCP is very easy to use. Basically, all you need to do is place MAGUUCP.EXE, ULFILE.EXE and DLFILE.EXE in the same directory, make that directory the current directory, then run MAGUUCP.EXE - you'll find everything you need to know by hitting your F1 key for help. You can also optionally place the file MAGUUCP.ICO in that directory if you wish to have a custom icon for MAGUUCP. Source code licensing to MAGUUCP is also available (see order form at the end of this manual). IBM is a trademark of International Business Machines, Inc. Hayes is a trademark of Hayes Microcomputer Products, Inc. USRobotics is a trademark of US Robotics Corporation Microsoft is a trademark of Microsoft Corporation Magnum BBS is a trademark of Gilmore Systems OS/2 is a trademark of IBM Corp. Portions of file xfer from Chuck Forsberg's public domain unix source, modified by Chuck Gilmore for OS/2 and MAGUUCP MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems MAGUUCP Communications Program for OS/2 Page 1-1 MAGUUCP's Initialization File (MAGUUCP.DAT) - Getting Started MAGUUCP reads your initialization file to send your modem the proper initialization parameters. This file is MAGUUCP.DAT and will be created if it does not exist. To alter this file, simply load it into your text editor and make the necessary changes. Note that when MAGUUCP creates this file, it assumes a 2400-baud modem. You'll need to change the baudrate and any other parameters with your text editor accordingly. Baudrates are also adjustable for each of the 200 phone numbers you can store in MAGUUCP's dialing directory (MAGUUCP.PHO). If you wish to create the MAGUUCP.DAT file yourself or modify the existing MAGUUCP.DAT file, you'll need to supply the following Keywords and Parameters: MODEM: USR HST DS v.everything BAUD: 57600 INIT1: AT &F1H0M1L3 INIT2: AT S7=60S0=0 INIT3: AT V1E1M1X7&K3 RESET: DEVICE: COM1 PARITY: N DATABITS: 8 STOPBITS: 1 OPENMODE: N CTSFLOW: Y The MODEM: keyword will accept up to an 80-character text line (including the MODEM: keyword) describing your modem as in the example above. The BAUD: keyword is the baudrate at which your modem will be initialized at. For modems that accept a higher DTE (computer to modem) speed than DCE (modem to modem) speed, you'll want to set this value at the highest DTE it can handle. In the above example, the USR HST DS v.everythnig modem is a 28800 baud modem but can accomodate a DTE speed of 57600. For those serial cards and communications drivers that support it, this modem can also accomodate a DTE speed of 115200 baud (NOTE: MUST BE SPECIFIED AS 1152 AS THE PARAMETER). The INIT1:, INIT2: and INIT3: parameters are modem initialization strings which can accomodate a text line (including the keyword) of up to 80 characters. You probably won't need to use all three fields but just in case you do, they are available. Note that some modems such as the Multitech 224Eh can only accept initialization strings of up to 40 characters each (hence three initialization fields). In your parameter strings, the \ (backslash) characer has special meaning, it starts an escape sequence: Use the \ character as the beginning of an escape sequence. If \\ appears, then a single \ character is sent. If \ is followed by one or more digits (up to 3 digits maximum), then the ASCII character represented by the decimal value of the digits will be sent (ie: \13 will send a CR character. If the \ is followed by MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems MAGUUCP Communications Program for OS/2 Page 1-2 MAGUUCP's Initialization File (MAGUUCP.DAT) - Getting Started a non-digit, that character will be sent. Furthermore, the each \~ sequence indicates a 500 milisecond delay (ie: \~\~ is a 1 second delay). The RESET: keyword holds your modem's reset string (usually AT Z) which can be up to 80 characters in length (including the keyword). The DEVICE: keyword defines the serial device that you wish MAGUUCP to use when it starts up. The parameter is usually COM1 or COM2, however, it can accept any valid serial device name (ie: AUX0, AUX1, COM8, \\SRVR\SERIAL1, etc). The PARITY: keyword can accept one of five possible parameters: N (none), E (even), O (odd), M (mark), or S (space). Usually, this setting is N (none). The DATABITS: keyword can accept one of four single digit numeric parameters (5, 6, 7 or 8). Usually this is 7 or 8. Most BBS's and dialup services are 8. The STOPBITS: keyword can accept one of four possible parameters (0, 1, 1.5, or 2). Usually, 1 is the normal value. The OPENMODE: keyword accepts a parameter of N (nonshared) or S (shared). The usual value for a multitasking operating system such as OS/2 is N (nonshared). If you choose S (shared), you run the risk of another program accessing the comport at the same time MAGUUCP is and loss of data into or out of the comport, along with other unpredictable results can occur. The CTSFLOW: keyword accepts a parameter of Y (yes) or N (no). The usual paramter here is Y (yes) which indicates that hardware flow control is to be used. If you specify N (no), unpredictable results can occur when you choose Xmodem-1K, Ymodem, Ymodem-G or Zmodem to upload files with. If you specify Y (yes), make sure your modem initialization string(s) (INITx:) contain your modem's command to tell it to use CTS flow control. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-1 Introduction MAGUUCP supports several special keystrokes which tell MAGUUCP to do something special. These special keystrokes can be an AltKey combination (example: <Alt-X> means to hold down your Alt key and press X). <PgUp> means to press the key on your keyboard labeled PgUp, and <PgDn> means to press the key on your keyboard labeled PgDn. Whenever you press one of these special keystrokes, your screen will usually clear, and you'll be presented with a prompt or menu. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-2 <Alt-A> ASCII send/capture or Cancel capture When you press your <Alt-A> key, you will get a prompt asking you if you want to [S]end a file to the remote computer via ASCII transfer, [R]eceive a file from the remote computer via ASCII transfer, or [C]ancel a currently running ASCII Receive. By choosing [R]eceive, you will be prompted for a filename. From this point on (or until you choose <Alt-A> again with the [C]ancel option), everything that you receive from the remote BBS or type to the remote BBS will be captured to the filename you supply. You can review this file anytime later on with your text editor, or print it on the printer. If you specify PRN as the filename, everything will be routed to your printer instead of to a file. NOTE: Binary file transfers (see <PgUp> and <PgDn>) will be excluded from being captured to the capture file. By choosing [S]end, you can send any ASCII text file up to a remote BBS. An example of where this would come in handy might be if you were to enter a message with your text editor, and upload this message in response to (Enter a message) on a remoter BBS. It would be like typing a message while online to the remote system, but instead of typing, it sends the characters in the file instead. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-3 <Alt-B> Toggle Bell on/off The <Alt-B> key combination toggles the bell on or off. If the bell is on, pressing <Alt-B> turns it off. If the bell is off, pressing <Alt-B> turns it back on. This is a handy feature when you or others don't wish to be disturbed by bell sounds. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-4 <Alt-D> Dialing Directory The dialing directory is brought to your screen when you press the <Alt-D> key. The dialing directory is self-explanatory. Basically, the dialing directory can hold up to 200 entries. Each entry consists of 7 fields: Entry Number: this is a 3-digit number ranging from 001 to 200. You needn't supply leading zeros to supply an entry number. Description of Host System: This field holds up to 35 characters describing the host system you'll be calling for this entry. The first entry in MAGUUCP has already been completed for you with the description and phone number of Gilmore System's Magnum BBS system (node 1). Modem telephone number: This field holds up to 25 characters describing the modem telephone number of the host system. Acceptable characters here are 0 thru 9, A thru Z, and the following characters (without the quotes): ",-*#" where the comma character (,) represents a 2-second delay to most modems. The hyphen character (-) is merely for readibility and is ignored. The asterisk (*) and pound (#) characters have special meanings to certain telphone systems. The letters of the alphabet (A thru Z) will be translated to the appropriate digits by MAGUUCP, therefore, telephone numbers such as 1-404-HI-MODEM are possible. The next field is the Parity field (see PARITY: keyword in the previous chapter for a description). Whatever is supplied here will override the PARITY: supplied in the initialization file when you choose to dial this entry, and will remain in effect until it is overriden by a different parameter in another entry you choose to dial. The next field is the Databits field (see DATABITS: keyword in the previous chapter for a description). Whatever is supplied here will override the DATABITS: supplied in the initialization file when you choose to dial this entry, and will remain in effect until it is overriden by a different parameter in another entry you choose to dial. The next field is the Stopbits field (see STOPBITS: keyword in the previous chapter for a description). Whatever is supplied here will override the STOPBITS: supplied in the initialization file when you choose to dial this entry, and will remain in effect until it is overriden by a different parameter in another entry you choose to dial. The last field is the BaudRate field (see BAUDRATE: keyword in the previous chapter for a description). Whatever is supplied here will override the BAUDRATE: supplied in the initialization file when you choose to dial this entry, and will remain in effect until it is overriden by a different parameter in another entry you choose to dial. NOTE: MAGUUCP can be made to dial an entry from the command-line by invoking MAGUUCP with the dial entry (denoted by the # character). Example: MAGUUCP #4 will dial entry #4, and if there's a script file associated with it, the script file will be read. (Demo scripts are limited to dial entry #1 and #2 only). As always, if MAGUUCP.0 is present, this will be the first file read regardless of how MAGUUCP is started. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-5 <Alt-E> Echo On/Off (full duplex/half duplex) By pressing your <Alt-E> key combination, you will toggle echo to/from on/off. Usually, BBS's will echo back every character you type - in this case, echo should be OFF. If you can't see what you're typing, MAGUUCP will echo what you're typing to the screen when you toggle echo back ON. If you are seeing double characters of each key you type, you should toggle echo OFF. Each time you press <Alt-E> it toggles (reverses) the current state of the echo. In other words, if local echo is ON, pressing <Alt-E> turns it OFF. Likewise, if local echo if OFF, pressing <Alt-E> turns it ON. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-6 <Alt-H> Hang Up Ocassionally, you'll need to manually disconnect your modem from a host system. For instance, if you're online to a remote system and can't figure out how to disconnect from it, or the remote system seems to be "locked up" (won't disconnect you), you can disconnect manually by pressing <Alt-H>. This will close the modem port and reopen it. If your modem does not respond to this, you will either have to look in your modem's user manual to see what you can add to the initialization strings to get it to respond, or you will have to manually turn your modem off. Usually, &C1&D2 parameters need to be included in one of your initialization strings. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-7 <Alt-L> Load/Unload/Pause ScriptFile <Alt-L> - Load/Unload/Pause ScriptFile. This function will prompt for L)oad: Load a new ScriptFile (filespec entry); U)nload: Unload (abort) the current ScriptFile; P)ause: Toggles pause on/off for current ScriptFile; NOTE: Not available in DEMO release! MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-8 <Alt-O> Shell to OS/2 Command Interpreter (CMD.EXE) While OS/2 is a multi-tasking operating system, getting to the OS/2 command interpreter (CMD.EXE) command line can be accomplished by simply switching to an OS/2 command window or OS/2 full-screen from the task list. However, we've received many requests for the ability to get to the command line directly via an Alt-Key combination from within MAGUUCP. Hence, the introduction of the <Alt-O> function. I assume this is for those of you who wish to use external file xfer protocols not directly supported by MAGUUCP. If this is the case, MAGUUCP's MAGUUCP.DAT file should contain S (shared) as the parameter to the OPENMODE keyword. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-9 <Alt-P> Set Lines/Page MAGUUCP can take advantage of your display's capability of displaying up to 100 lines per screen page. Simply press <Alt-P> to choose a new setting. NOTE: If your display is capable of displaying, say, 25, 28, 43 or 50 lines per screen, then entering any value in response to this prompt will result in the nearest capability that your monitor offers. For example, if you enter 68 lines/screen, MAGUUCP will change this to 50 lines/screen. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-10 <Alt-Q> and <Alt-S> (XON and XOFF) [Resume and Pause] MAGUUCP can send XON (resume transmit) and XOFF (halt transmit) to whatever host you're connected to. Simply put, XOFF tells the host (BBS) to halt transmission until you instruct it to resume with an XON instruction. The <Alt-S> key combination will send an XOFF instruction to the host, while the <Alt-Q> key combination will send an XON instruction. NOTE: Sending an <Alt-S> (XOFF) to the host will stop the host from further transmission of text, however, the modem on the host may continue to send characters to you until its buffer is cleared! Note that XON and XOFF are reserved for ASCII (text) mode. Your modem should be configured to treat XON/XOFF characters as data (ignore them) otherwise binary file transfers will fail! MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-11 <Alt-R> Review Buffer MAGUUCP stores all incoming/outgoing characters (except for binary file transfers) in a circular buffer of about 16K. By pressing <Alt-R>, you can review what's in the buffer, clear the buffer, or write the contents of the buffer to a disk file. When you press <Alt-R>, you will be looking at the top of the buffer. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-12 <Alt-X> Exit MAGUUCP By pressing your <Alt-X> key, MAGUUCP prompts you as to wheter you want to exit the program or not. If you type Y (yes), MAGOM will end, otherwise if you type N (no), MAGUUCP will return to normal operation. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-13 <PgUp> Transmit Binary File to Host. When you press your <PgUp> key, MAGUUCP will prompt you first for an upload protocol to use for sending a file to the remote system, then for the filename you wish to send. Usually, you'll first tell the remote system which file you'll be sending and the protocol you'll be using to send it with. You must choose the same protocol with MAGUUCP but the filename doesn't necessarily have to match. If you supply a blank for either prompt, MAGUUCP will return back to terminal (normal) operation. If you supply a protocol and filename, MAGUUCP will call the ULFILE.EXE program (expected to be in the same directory as MAGUUCP.EXE) to transfer the file with. You'll see the copyright information and the file will be sent. When the file is finished being sent, MAGUUCP will return to normal operation. You can abort the xfer by pressing <Ctrl-X> many times. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-14 <PgDn> Receive Binary File from Host. When you press your <PgDn> key, MAGUUCP will prompt you for a download protocol to use for receiving one or more files from the remote system. If you choose a Single-File protocol (Xmodem, Xmodem-CRC, Xmodem-1K), MAGUUCP will prompt you for a filename to store the received file in. If you choose a batch protocol (Ymodem, Ymodem-G, Zmodem), MAGUUCP will immediately begin the transfer, and the names of the files you'll be receiving will automatically be sent to you by the host system. Whatever protocol you choose to receive files with, it must match the same protocol that you've chosen for the host (remote) system to use. Note that if you're connected to a host system which sends the auto-zmodem sequence, MAGUUCP will recognize this and begin the transfer for you... you needn't bother pressing your <PgDn> key. Magnum BBS host systems will send the auto-zmodem sequence. If you supply a blank at any prompt, MAGUUCP will return back to terminal (normal) operation. MAGUUCP begins the transfer by calling the DLFILE.EXE program (expected to be in the same directory as MAGUUCP.EXE) to trasnfer the file with. You'll see the copyright information and the file(s) will be received. When the transfer completes, MAGUUCP will return to normal operation. You can abort the xfer by pressing <Ctrl-X> many times. NOTE: If you've downloaded a file with Zmodem and you get disconnected in the middle of a transfer, or the transfer aborts for any reason, you can call the remote system again and start the same Zmodem transfer again, but choose the [R]ecoverZmodem option instead of [Z]modem - this will cause the transfer to resume from where it left off. If the host sends an 'auto-zmodem' sequence, MAGUUCP will recognize this and handle it for you (you needn't bother pressing <PgDn>). Magnum BBS systems send the 'auto-zmodem' sequence. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Using MAGUUCP Page 2-15 When Online with a "Magnum BBS" System When you're online with a "Magnum BBS" System, MAGUUCP will let you use the following keys when using the ANSI message editor or NotePad facility of the Magnum BBS: Up, Down, Right, Left ARROW keys... Moves cursor accordingly. <Home> ............................ Move to beginning of current line. <End> ............................. Move to end of current line. <Ins> ............................. Insert a space at cursor position. <Del> ............................. Delete character at cursor position. <Ctrl-PgUp> ....................... Move up (back) one screen. <Ctrl-PgDn> ....................... Move down (forward) one screen. Note that the <PgUp> and <PgDn> keys by themselves are reserved for initiating a binary file transfer and are therefore not used in the ANSI message editor. Use <Ctrl-PgUp> and <Ctrl-PgDn> instead. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Script Files Page 3-1 Introduction USING SCRIPT FILES ------------------ Script files are a way of automating communication between MAGUUCP and any BBS or other host that you're calling. Most terminal programs which utilize a scripting language employ a "expect"/"response" technique. MAGUUCP also employs this technique but also offers a "whenever" technique (ie: whenever a certain character string is received, send a predefined response). Script files conform to the naming convention: MAGUUCP.nnn where nnn is a 1 to 3 digit number indicating the dial record entry (examples: maguucp.1, maguucp.20, maguucp.134, ... no leading zeros). These script files are ASCII text files of the format (via example): whenever "press enter" send "\~\13" waitfor "service" send "holonet\13" waitfor "login" send "myname\13" waitfor "password" send "mypassword\13" waitfor "terminal" send "uucp\13" whenever "NO CARRIER" call <alt-x> [parms] **NOTE: MAGUUCP.1 and MAGUUCP.2 are the only valid script files in the DEMO release. MAGUUCP.0 is also available in the DEMO release. Script files are read/processed whenever a dialing entry is chosen, just before MAGUUCP dials that number. The only exception is the MAGUUCP.0 file which is read/processed upon startup. Script files are read in their entirety, one line at a time, until all lines are read. Anything starting with the keywords 'whenever' or 'waitfor' are stored in memory. All other statements are executed as they're read. When the file is completed, the number is dialed. Script files are CASE SENSITIVE, and the following keywords MUST be entered in lowercase: ; lines starting with a ; character are comments (ignored) whenever "string" or "string1&&string2" or "string1||string2" waitfor "string" or "string1&&string2" or "string1||string2" send "string" call <alt-n> init <alt-n> include "d:\path\filename.ext" echo "string" local to screen only runpgm "pgnmane.exe parms"[,HOW] HOW: WAIT, NOWAIT, DETACH set case independent|dependent (for incoming whenever & waitfor) set uucp_protocol t (UUCP protocol to use, default=g) set caller_hostname hostname (UUCP name of YOUR system) set called_hostname hostname (UUCP name of system you're CALLING) set workdir (work dir - must match Magnum work dir for use with UUCP only) set dldir (download dir for x/y/zmodem downloads set uucp_timeout n (uucp inactivity timeout [n=minutes]) set redialct nn [[exit] xx] sets redial count (ie: set redialct 30 MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Script Files Page 3-2 Introduction the default (if not specified) is 30 optional: if 'exit' specified pgm ends with optional exit value xx set dialprefix string sets dialprefix to string (no alpha) set dialsuffix string sets dialsuffix to string (no alpha) All of the parms are strings within double quotes. These quoted strings may also contain escape sequences: Uses the \ character as the beginning of an escape sequence. If \\ appears, then a single \ character is sent. If \ is followed by one or more digits (up to 3 digits maximum), then the ASCII character represented by the decimal value of the digits will be sent (ie: \13 will send a CR character. If the \ is followed by a non-digit, that character will be sent. Furthermore, the each \~ sequence indicates a 500 milisecond delay (ie: \~\~ is a 1 second delay). As of this writing, you may have up to 400 'whenever' and 'send' text lines, and up to 400 'waitfor' and 'send' text lines. Each quoted string may not exceed 40 characters in length. ** NOTE: only 4 'whenever'/'send' and 4 'waitfor'/'send' text lines are allowed in the DEMO release. The call statement can be used in lieu of a 'send' statement. The parameter to a call statement must be in the form of <alt-x> where 'x' is an alt-key command. Note that < and > are used instead of double quote characters. Multiple parms are separated with ; characters. The init statement is identical to the call statement except that it is executed immediately and not stored. All init statements in a file are executed prior to storing the rest of the file. The include statement is of the format: include "d:\path\filename.ext" and halts processing of the current script to 'include' the 'included' script file. After the 'included' script is finished, processing continues with where it left off prior to the include. Include's can be nested up to 20 levels (ie: main script can 'include' another script which can 'include' another, which can 'include' another, etc... up to 20 times). The following is a working example of a script file used for calling Exec-pc (a popular BBS system in Milwaukee). Assuming the dial entry is entry #5, then the following script would be in file MAGUUCP.5: set dldir e:\dldir\execpc whenever "CONNECT" send "\13" whenever "ANSI Color Graphics? (y/N) ->" send "y" waitfor "FIRST name ->" send "joe;smith;mypassword\13" waitfor "TOP Menu (?=HELP) ->" send ";f;e;n\13" MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Script Files Page 3-3 Introduction whenever "Would you like to read bulletins now? (" send "n" whenever ">>More?" send "\13" whenever "NO CARRIER" call <Alt-R> s The following is an example of a script file to log you onto Compuserve: whenever "CONNECT" send "\3\13" waitfor "D:" send "22222,1111\13" waitfor "ssword:" send "mypassword\13" In many cases, a poor or noisy line can be corrected by forcing an AT&T line. In the U.S., you can force an AT&T line by placing the following in your script file(s): set dialprefix 10288 MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems UUCP Communications Protocol Page 4-1 Introduction UUCP, which stands for "Unix to Unix Copy Program" is the communications protocol in which MAGUUCP and your Internet Service Provider (ISP) uses to perform Internet E-mail exchange (hence the name "MAG" [for Magnum] "UUCP" [for UUCP]). In that the Internet is Unix based, UUCP has been the standard communications protocol for file (mail) exchange for a long time. UUCP communications supports many different UUCP protocols, each of which is named after a single letter. The UUCP protocols which MAGUUCP supports are: e, f, g, t, T, and y. NOTE: As of this writing, the g protocol is not yet fully operational, but should be with the next release. The g protocol is the original (and standard) UUCP protocol, but for now you'll need to use one of the other protocols. The protocol which MAGUUCP uses can be specified as the uucp_protocol parameter in your script file(s) (explained later in this chapter). Note that not all ISP's support all protocols (there are many), and neither does MAGUUCP. Of the protocols MAGUUCP supports: e - No flow control or error checking; intended for networks providing reliable end-to-end connections. Not tested as of this writing. f - A 7-bit streaming protocol; not flow controlled; originally intended for transmission over X.25 PAD links. Tested as of this writing. g - Packet based, flow controlled error correcting protocol that requires an 8-bit clear connection; the original UUCP protocol and supported by all UUCP implementations. Tested but not working correctly in MAGUUCP as of this writing. t - Intended for use on links which provide reliable end-to-end connections; no error checking or flow control; requires an 8-bit clear channel. Tested and working correctly. T - Same as t but doesn't require a 'reliable' connection (used in Taylor UUCP v1.06). y - Packet based streaming protocol designed for communication lines which handle error correction and flow control; requires an 8-bit clean connection; performs error detection but not error correction: when an error is deteced, the line is dropped; efficient over a half-duplex communication line such as PEP. Used in Taylor UUCP v1.06. Tested but has a few bugs as of this writing. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems UUCP Communications Protocol Page 4-2 Setting up a UUCP script file In that MAGUUCP is designed to be the UUCP interface between Magnum BBS systems and your ISP, we'll be covering Magnum BBS in this chapter as well. Magnum BBS is NOT a requirement for UUCP communications, and later on we'll show how you can use MAGUUCP for your own applications. To set up your Magnum BBS system for Internet E-mail capabilities, you must first have: 1) An Internet Service Provider (we recommend "Info Access Technologies", also known as Holonet). Voice: (510) 704-0160, Modem: (510) 704-1058. 2) UUCP Domain Name Service (this takes about 3 weeks for your Internt Service Provider to set up). UUCP Domain Name Service means that your BBS will be known as somename.com (for us, its gilmore.com). The users on your BBS will be known as someuser@somename.com (using our site as an example: joe@gilmore.com, susan@gilmore.com, postmaster@gilmore.com, etc). Once you have the above set up, you will now be able to implement the Internet E-mail capabilities of Magnum BBS as follows: 0) If you're not using a Magnum BBS system, skip to step 9. 1) First, you'll need the MAGUUCP.EXE program (this program). This is NOT included with your Magnum BBS system and is available for purchase from Gilmore Systems. 2) If you haven't set up an "OUTSIDE MAIL" account, you will need to log onto the system (from the console) using OUTSIDE for 'first name' and MAIL for 'last name' (don't use a middle name). Once the system has added 'OUTSIDE MAIL' as a new user, log off! Jot down the ID number for the new OUTSIDE MAIL account. NOTE: If you already have an OUTSIDE MAIL account set up, skip to step 3. 2a) Log on as Sysop. Go into the Sysop menu, USER Database Area. Pull up the account for the OUTSIDE MAIL ID that you just created. Change the TYPE parm (2nd line from top of screen) to type O (O is for OUTSIDE MAIL). Increase the security level to that which has access to all of the message bases and message areas that you wish this account to have access to. Change the MSG_?_AREAS (near bottom of screen) accordingly. If you have the Extended Msgbase module and are using MSG GROUPS, change the MSGGRP parm accordingly. 2b) Shut down your BBS (* endnow) and edit all of your STARTUP.n files such that the OUTSIDE_MAIL_ID: parameter reflects the id number of this new OUTSIDE MAIL account. Example: if your OUTSIDE MAIL account id is /1407, then you should provide this as the parm as follows: OUTSIDE_MAIL_ID: /1407 MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems UUCP Communications Protocol Page 4-3 Setting up a UUCP script file 3) Shut down your BBS (* endow) and edit all of your STARTUP.n files as follows (changing the following parms): INTERNET_DOMAIN_NAME: gilmore.com (this will be YOUR domain name, like ibm.com or xyzcorp.com). INTERNET_TIMEZONE: PST (PST=Pacific Standard Time, PDT=Pacific Daylight Time, EST=Eastern Standard Time, MDT=Mountain Daylight Time, CST=Central Standard Time, etc). ALLOW_OUTSIDE_MAIL: Y Save the changes and recompile the STARTUP files (makembbs.exe). Restart your BBS. 4) Log on (* logon) as a new user using the account name EMAIL ACCOUNT (EMAIL for first name, ACCOUNT for last name). After this new account id is added, log off! Log on (* logon) As SYSOP (/0) and go into the Sysop Menu, USER Database Area. Pull up the account for the id number of the EMAIL_ACCOUNT. Change the account TYPE (2nd line from type) to E (for E-MAIL). Change MSG_?_AREAS according to the areas you wish this account to have access to. Change the MSGGRP (If you're using GROUPS and you have the Extended MsgBAse Module) accordinly if desired. IMPORTANT: Change the LEVEL (security level) to that of the security level of the SYSOP_MAIL_LVL parm in your STARTUP files. This is important because this account needs to be able to read PRIVATE mail (this is only allowed with a security level of what you have for SYSOP_MAIL_LVL or greater). You can even give it a level to match that of the Sysop if you wish. This is NOT a user account, its an EMAIL account! Once the changes are made, log off. 5) If you haven't done so already, set up MAGUUCP.EXE. Make note of the directory name you're installing this program into (ie: d:\maguucp). NOTE: SEE STEP 9 (below) FOR OUR SETUP. 6) In your PGM_DIR (ie: d:\magnum\pgm_dir), create a command file by the name of INTERNET.CMD with your text editor. The contents of the file are: d: cd \magnum\pgm_dir d:\magnum\rje_dir\msglist mbbsinit.3 NNN * u y * * email.out e* cd \maguucp maguucp #NN MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems UUCP Communications Protocol Page 4-4 Setting up a UUCP script file cd \magnum\pgm_dir emailin mbbsinit.3 NNN d:\magnum\ses_dir\email.prm echo N active >tmp.ace exit - In the above, the first line is the drive letter of the drive that your Magnum BBS is installed on (your \magnum\pgm_dir). - The second line changes the directory to your \magnum\pgm_dir. - The third line executes the msglist program. The NNN parm should be the ID number (without the / character) of the OUTSIDE MAIL account that you created in step 2. If your drive letter is not d:, change it to the drive letter that your \magnum\rje_dir is on. We're assuming that you're using node 3, therefore we've supplied mbbsinit.3 on this line. Change the 3 to whatever node you'll be using for your MAGUUCP program. - The fourth line changes to the directory that you installed your MAGUUCP program in (assuming same drive letter as that of your Magnum system... if different, insert a line before this containing the driver letter that its on followed by a colon [ ie: c: ] ). - The fifth line invokes the MAGUUCP program to call your Internet Service Provider (replace the NN with the dialing directory entry for your Internet Service Provider; if its entry #4 for example, you'd supply: maguucp #4). Make sure you've set up your script file for MAGUUCP.NN (or MAGUUCP.4 using our example) as provided in the MAGUUCP documentation. - The sixth line changes back to your \magnum\pgm_dir (assumes that your \magnum\pgm_dir is on the same drive as \maguucp; if it isn't insert a line containing the drive letter of your \magnum\pgm_dir followed by a colon [ ie: c: ] ). - The seventh line processes incoming email and places it in the proper areas of your Magnum BBS system. Change the NNN to reflect the id number (just the number, no / character) of the OUTSIDE MAIL account (same as in line 3). If the drive letter of your \magnum\ses_dir is not d:, change it to the drive letter that your \magnum\ses_dir is on. Create the file EMAIL.PRM in your \magnum\ses_dir with the following contents: headers: n msgbase: 0 area: a Where the 'headers:' parm can be one of N (no headers), Y (all headers), or P (partial headers). If you choose N, incoming mail text will look like it always does. If you choose Y, incoming mail text will include all of the headers including routing information of all the systems that the mail went through before arriving at your system. If you chhose P, then all headers OTHER than routing information will be shown. - The eigth line restarts the node that was shut down (made inactive) in order to use the modem for MAGUUCP. Replace the N with the node number of the node that was shut down (made inactive). - The ninth (last) line exits the command file. 7) Modify your \magnum\pgm_dir\mbbs.ace file (or create it if you don't have one) with the following commands (we're going to use MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems UUCP Communications Protocol Page 4-5 Setting up a UUCP script file node 3 for the node to be shut down in our example, you should replace this with the node number you wish to use for your system). We're also assuming that your system will be calling your Internet Service Provider at 02:00 (2 AM) every day: 0123456,01:00,3 shutdown 02:00 0123456,02:01,"start internet.cmd",nowait If you wish to have your system call more than once/day, duplicate the above two lines changing 01:00 to one hour before wishing to shut down the node, change 02:00 to the time you want the node shut down, change 02:01 to the time you want maguucp started. 8) In your STARTUP files prior to step 3 above, if your parm to the ALLOW_OUTSIDE_MAIL was N, you'll need to write a .mex program to change the users in your USER database to allow them access to outside mail. The .mex program should be created in your \magnum\pgm_dir with a name of UPDT.MEX (or something similar). The contents of the file would be: #CONFIG_FILE: mbbsinit.1 #LOG_FILE: nul #DATABASE: user #START @outside_mail = true #STOP The above simple .mex program will change all users to allow them access to outside mail. If you wish to have only a certain security level or higher to have access (say, level 100 for example), change the program statement (between #START and #STOP) to: if(@level >= 100) { @outside_mail = true } Run the program: MBBSEXEC UPDT 9) For setting up the MAGUUCP scripts, first make certain you've made a dialing directory entry for your Internet Service Provider. Lets Assume this is entry #4. Create the file MAGUUCP.4 in the same directory that your MAGUUCP.EXE program resides in. The contents of MAGUUCP.4 will look similar to the following (assuming you're using Holonet as your Internet Service Provider): set caller_hostname gilmore set called_hostname holonet set workdir d:\magnum\work_dir\3 set uucp_protocol g MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems UUCP Communications Protocol Page 4-6 Setting up a UUCP script file whenever "CONNECT" send "\13\~\~holonet\13" whenever "HoloNet Member Name" send "cgilmore\13" waitfor "assword:" send "mypassword\13" waitfor "erminal" send "uucp\13" - In line one above, the caller_hostname is set to our UUCP domain name (without the .com). - The second line sets the called_hostname to holonet (the Internt Service Provider). - The third line matches the work_dir defined in the STARTUP.3 file because we've used mbbsinit.3 (the compiled startup.3 file) in our example in step 6 above. All incoming and outgoing email temporary storage is held in this work directory. NOTE: If not using Magnum BBS, supply any directory name in which you wish incoming/outgoing e-mail to be plaed in (make sure you create the directory first). - The fourth line sets the UUCP protocol to g. Note that MAGUUCP currently has 6 of the UUCP protocols coded: e = not supported by Holonet, not tested as of this writing. f = supported by Holonet and nearly every other Internet Service Provider. Tested. Works well transmitting, flaky on receiving. g = the standard (and default) uucp protocol supported by all uucp packages. Tested. t = supported by Holonet if using uucp-1.06 as your terminal type. Tested. T = Same as t but for uucp versions less than 1.06 (ie: if you supply uucp as your terminal type instead of uucp-1.06). Note that uucp-1.06 works with Holonet, but may not work with other providers. If you have a different provider, use uucp instead of uucp-1.06. Tested. y = Supported by Holonet using uucp-1.06. There are bugs with this protocol as of this writing (this is a NEW protocol, so your provider may not support this yet). Note that when we refer to uucp-1.06 above, it refers specifically to a UUCP implementation known as Taylor UUCP v1.06. - The fifth line looks for the CONNECT string from your modem (make sure you're using Verbose modem codes [ ie: AT V1 ] ) and sends holonet as the name to connect to. This line is not needed if you're calling Holonet directly at their Berkely, CA number. It is needed if you're calling via a local access telephone number. - The sixth line answers the "Holonet Member Name" prompt with cgilmore. Change this to your member name (your Internet Service Provider will provide you with one). - The seventh line answers the "password" prompt with your password. Change the mypassword string to your password. Note that the beginning P of Password is intentionally absent because it may appear in upper or lowercase, and we need to match this exactly. - The eigth (last) line answers the "terminal" prompt with the type of terminal you wish. Note that the beginning T of Terminal is intentionally absent because it may appear in upper or lowercase, and we need to match this exactly. The rest will be automatically handled by MAGUUCP. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems UUCP Communications Protocol Page 4-7 Setting up a UUCP script file For those using Magnum BBS: when MAGUUCP finishes, the INTERNET.CMD file which started it will then start the EMAILIN.EXE program to process the incoming mail. IMPORTANT: Once a UUCP session has been established, MAGUUCP will exit (terminate) once finished, or if carrier is dropped. This is not true of any other connection. This is done such that a .CMD file that called MAGUUCP can continue with the next command in the .CMD file. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Format of MAGUUCP's e-mail (technical) Page 5-1 Introduction This section reveals the technical specifications which MAGUUCP uses for Internet E-mail. This will allow you to write applications that can supply MAGUUCP with outgoing e-mail and process incoming e-mail using MAGUUCP as the transport mechanism. This section is intended only for programmers who wish to use MAGUUCP as the interface (such as uucico under Unix). Anyone who's tried to use a UUCP package will appreciate how easy MAGUUCP is to use and set up, and will readily appreciate the simple format in which MAGUUCP uses to process mail to/from your ISP. If you're a programmer wishing to write a mail system but doesn't know the first thing about data communications (and doesn't want to, or just doesn't want to deal with the communications headaches), then this section is for you! All other readers are welcome to peruse this section but it is not required. The format that we've devloped was designed to work with the lowest common denominator in file system naming conventions: FAT (this file format is what's used by DOS, and can be used by Windows, OS/2 and other file systems). FAT is an 8.3 (eight character filename, a period, and three character extension) for a total of 12 characters maximum per filename. Unix systems use 14-character filenames. The format we've developed will work with all file systems in that all of the filenames are contained within one file (email.out) as described on the next page, hence 14-character filenames are no restriction on FAT systems. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Format of MAGUUCP's e-mail (technical) Page 5-2 Input E-mail file to MAGUUCP The input e-mail file is named EMAIL.OUT (extension of .OUT because its OUTGOING from your computer, but input to MAGUUCP). Any e-mail you wish to send thru the Internet via MAGUUCP must be contained within this file. Note that this file is expected to be found (if it exists) in the "workdir" parm of your maguucp.xx script file. The format of the file is: 0x03C.mmddhhmmsshh - That's hex 3 (binary 3, or <ctrl-c> followed by the letter C, a period (.), then the following naming convention: mmddhhmmsshh, which breaks down into: mm - current month at time of entry dd - current day at time of entry hh - current hour mm - current minutes ss - current seconds hh - current hundredths of seconds S D.mmddhhmmsshh D.mmddhhmmsshh sender - D.mmddhhmmsshh 0666 - where "S " is a given (unchangeable), D.mmddhhmmsshh matches mmddhhmmsshh from the previous line, D.mmddhhmmsshh (the 2nd one) has a unique last digit (the last 'h'), our algorithm is to use alpha letters (ie: 0 becomes A, 1 becomes B, 2 becomes, C, ... 9 becomes J). sender is the name of the person who's sending this message (without the @ or anything to the right of it). - the '-' character MUST be present, and must be preced and succeeded by a space character. D.mmddhhmmsshh (the 3rd one) matches the first one on the line. 0666 must be present. 0x03D.mmddhhmmsshh - That's hex 3 (binary 3, or <ctrl-c> followed by the letter D, a period (.), and the rest is should match the name of the first line. The rest is the Internet E-mail message header (no blank lines so far), via Example: From cgilmore, Mon 05Feb1996 18:04:17 PST Received: by gilmore.com (Magnum BBS/Internet Processor v8.08B33) Mon, 05 Feb 1996 18:04:17 PST Date: Mon, 5 Feb 96 18:02:05 PST From: "Chuck B Gilmore" <cgilmore@gilmore.com> Message-ID: <0.E2051043.A15.cgilmore@gilmore.com> Organization: Gilmore Systems -Home of MAGNUM OS/2 BBS To: susan@xyzcorp.com MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Format of MAGUUCP's e-mail (technical) Page 5-3 Input E-mail file to MAGUUCP Subject: HI! and now the message text (a blank line separates the headers from the message text): Hello there Susan, this is a test e-mail message being sent to you from me. Let me know how the weather is today! - Chuck For a more detailed description of the Internet E-mail headers, visit your local bookstore for a good book on the subject (or ask your ISP for the RFC document pertaining to Internet E-mail internals). It is beyond the scope of this manual to cover Internet E-mail message format. Continuing on, the next line is the same as the first line: 0x03C.mmddhhmmssyy (note that the first m of mm in this line should be be incremented by 4 (a 0 becomes a 1, and a 1 becomes a 2). S D.mmddhhmmsshh X.mmddhhmmsshh sender - D.mmddhhmmssyy 0666 All of the mmddhhmmssyy are identical to the above mmddhhmmssyy except that the 2nd one's last digit is changed to alpha as in the previous example. Note that the 2nd mmddhhmmsshh is preced by X. 0x03X.mmddhhmmssyy (hex 3 first, followed by X.mmddhhmmssyy where mmddhhmmssyy matches the first mmddhhmmssyy in the previous line. U cgilmore gilmore (U sender, uucp name) F D.mmddhhmmssyy (F filename [matches 2nd mmddhhmmssyy above) I D.mmddhhmmssyy (I filename [matches above] Z (static) R cgilmore@gilmore.uucp (note .uucp instead of .com) C rmail susan@xyzcorp.com (who to send to) The above completes one E-mail message stored and ready for input to MAGUUCP. To send more, simply append to this file using the same format as above (get a new mmddhhmmssyy for each message). Here's a working example of what an EMAIL.OUT file with two messages to send might look like: <Ctrl-C>C.020518041765 S D.020518041765 D.02051804176F cgilmore - D.020518041765 0666 <Ctrl-C>D.020518041765 From cgilmore, Mon 05Feb1996 18:04:17 PST Received: by gilmore.com (Magnum BBS/Internet Processor v8.08B33) Mon, 05 Feb 1996 18:04:17 PST Date: Mon, 5 Feb 96 18:02:05 PST MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Format of MAGUUCP's e-mail (technical) Page 5-4 Input E-mail file to MAGUUCP From: "Chuck B Gilmore" <cgilmore@gilmore.com> Message-ID: <0.E2051043.A15.cgilmore@gilmore.com> Organization: Gilmore Systems -Home of MAGNUM OS/2 BBS To: susan@xyzcorp.com Subject: HI! Hello there Susan, this is a test e-mail message being sent to you from me. Let me know how the weather is today! - Chuck <Ctrl-C>C.420518041765 S D.420518041765 X.42051804176F cgilmore - D.420518041765 0666 <Ctrl-C>X.420518041765 U cgilmore gilmore.com F D.42051804176F I D.42051804176F Z R cgilmore@gilmore.uucp C rmail susan@xyzcorp.com <Ctrl-C>C.020518041806 S D.020518041806 D.02051804180G cgilmore - D.020518041806 0666 <Ctrl-C>D.020518041806 From cgilmore Mon, 05 Feb 1996 18:04:18 PST remote from gilmore Received: by gilmore.com (Magnum BBS/Internet Processor v8.08B33); Mon, 05 Feb 1996 18:04:18 PST Date: Mon, 5 Feb 96 18:02:08 PST From: "Chuck B Gilmore" <cgilmore@gilmore.com> Message-ID: <0.E2051043.A38.cgilmore@gilmore.com> Organization: Gilmore Systems -Home of MAGNUM OS/2 BBS To: info@someplace.com Subject: INFO REQUEST Information request please... <Ctrl-C>C.420518041806 S D.420518041806 X.42051804180G cgilmore - D.420518041806 0666 <Ctrl-C>X.420518041806 U cgilmore gilmore F D.42051804180G I D.42051804180G Z R cgilmore@gilmore.uucp C rmail info@someplace.com If a 3rd (or subsequent message) were to be present, repeat the same format for the third message. No limit on how many messages can be sent or placed in the EMAIL.OUT file. Note that if your application runs again prior to MAGUUCP processing the EMAIL.OUT file, your application should append to this file! MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Format of MAGUUCP's e-mail (technical) Page 5-5 Output E-mail file from MAGUUCP The output e-mail file is named EMAIL.IN (extension of .IN because its INCOMING from your ISP to your system via MAGUUCP). Any e-mail received will be placed in this file, and has been designed to be used on any file system including FAT. If any incoming mail is received, this file will exist with a length (file size) greater than 0 and will be found in the "workdir" parm o your maguucp.xx script file. The format of the file is (via working example with 2 incoming messages): <Ctrl-C>C S D.0Ea5 D.holonet50EA5 daemon - D.0Ea5 0666 cgilmore@gilmore.com d:\magnum\work_dir\3\$223109$.047 <Ctrl-C>C S D.X0EAE X.holonetN0EAE daemon - D.X0EAE 0666 cgilmore@gilmore.com d:\magnum\work_dir\3\$223113$.065 <Ctrl-C>C S D.0EA8 D.holonet50EA8 daemon - D.0eA8 0666 cgilmore@gilmore.com d:\magnum\work_dir\3\$223117$.050 <Ctrl-C>C S D.X0EAF X.holonetN0EAF daemon - D.X0EAF 0666 cgilmore@gilmoer.com d:\magnum\work_dir\3\$223121$.00i Every 6 lines comprise an incoming message. The first line is a hex 3 followed by C (<Ctrl-C>C). This indicates that the next line will be the UUCP "S " command as it came in. The next (2rd) line is the UUCP "S " command as it came in. All you really need to scan that line for is whether or not there's an "X." within the line... if there isn't, its the message text file (with header info), otherwise its a UUCP "X." file. The next line (3rd line) is a filename in which the message header and text is stored. The 4th line is another <Ctrl-C> indicating that the next line is a UUCP "S " line. The 5th line is the UUCP "S " command as it came in (scan for " X." within the file to ensure that its a UUCP X file. The 6th line is the filename of where the X commands for the previous file (message text file) is stored. Any additional lines: repeat the above procedure for each group of 6 lines. If the 3rd line of any group of 6 lines contains the string " news ", then th file is a news file and not an e-mail file (have your program act accordingly as news can be batched, compressed, or both). After processing each group of 6 lines, the 2 input files (message and X file should be closed and deleted prior to processing the next group of 6 lines. If your program doesn't process the EMAIL.IN file prior to the next time MAGUUCP receives more mail, MAGUUCP will append to the existing file (it will create the file if it doesn't exist). Its beyond the scope of this manual to cover UUCP "S " commands and X files, but this implementation has made it quite easy. In the X file, your application should search for a line containing "C rmail ", becuase the name following this (ie: C rmail john) is who the message is addressed to (ie: if your domain name is xyz.com, then mail would be sent to john@xyz.com). MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Order Form for Commercial Release of MAGUUCP v3.00C Page 6-1 "MAGUUCP v3.00C for OS/2" Order Form ------------------------------------ Complete the form, and mail it with your remittance to: Gilmore Systems 7354 Rubio Ave. Van Nuys, CA 91406 - U.S.A. - OR - Fax the form with credit card information to: (818) 782-2093 - OR - Place your order with us by phone at: (818) 782-1870 - OR- Place your order via credit card ONLINE on our BBS at: (818) 782-6290 ------------------------------------------------------------------------------ Quantity Product Description Price Total -------- ----------------------------------------------- -------- -------- ___ MAGUUCP v3.00C for OS/2 $ 40.00 ________ ___ Shipping/Handling (U.S.=$3, Canada=$4, Other=$5) ________ ________ ___ Sales Tax (California Destinations Only) ________ ________ TOTAL: $ ________ ======================================================== Ship To: < Be certain to fill < in the "Ship To" < Information!! < < PURCHASE ORDERS: < U.S.-based companies ======================================================== w/ Dunn & Bradstreet number ONLY! Telephone Number: ____________________________ ---------------------------- For Credit Card Orders Only: ---------------------------- Check One: ____ VISA ____ MASTERCARD ____ AMERICAN EXPRESS Card Number: ______________________________________ Expiration Date: _________ Your (CardHolder) Name: ______________________________ Today's Date: _________ Signature of CardHolder: _____________________________________________________ MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Distribution Rights & Source Code Licensing Page 7-1 Distribution Rights ------------------- You may NOT license, sell, bundle, transfer or otherwise distribute this program without obtaining a license to do so from Gilmore Systems. A distribution license will be issued to you provided you pay the one-time Distribution Licensing fee. This fee varies depending on the information you supply us with (contact us for information on licensing fees). Source Code Licensing --------------------- Source code licensing is available provided you PRE PAY (no purchase orders) the license fee (order form on next page) and SIGN the nondisclosure agreement on the two pages following the order form. Return all three pages to Gilmore Systems with your remittance and signature. MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Distribution Rights & Source Code Licensing Page 7-2 Source Code Licensing Order Form (MAGUUCP) ------------------------------------------ NOTE: Non-Disclosure agreement on next two pages MUST accompany your order or it will NOT be processed! Payment in U.S. funds ONLY! I am placing an order for source code licensing to MAGUUCP software from Gilmore Systems. I am enclosing the signed 2-page non-disclosure agreement, along with $100 remittance (plus shipping and any sales taxes) by: (check one) ___ Check or other bank draft in U.S. dollars ___ Cash ___ Visa / MasterCard ___ EuroCard ___ American Express (or Optima) Licensing Fee............................................. $ 100.00 Shipping/Handling (U.S. = $3, Canada = $4, others = $6)... $ ______ Sales Tax (California Destinations Only).................. $ ______ Total: $ ______ Ship To: ________________________________________ ________________________________________ ________________________________________ ________________________________________ ________________________________________ Daytime Phone# (include area code): __________________________ This section for Credit Card orders ONLY: Card Number: __________________________________ Expiration Date: _________ Your (CardHolder) Name: __________________________ Today's Date: _________ Signature of CardHolder: _________________________________________________ MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Distribution Rights & Source Code Licensing Page 7-3 NON-DISCLOSURE AGREEMENT This document by and between Gilmore Systems (hereinafter referred to as LICENSOR) and _________________________________ (hereinafter referred to as LICENSEE) shall serve as a contractual agreement between LICENSOR and LICENSEE for the source code modules of LICENSOR's "MAGUUCP" software. Upon receipt of the $ 100 licensing fee and receipt of this signed agreement from LICENSEE to LICENSOR, LICENSOR will provide on diskette to LICENSEE an AS IS copy of the v3.00c source code of the "MAGUUCP" software, and a copy of this executed agreement. Copyright, Trademark, Ownership, Distribution, Marketing and all other rights are retained by LICENSOR. LICENSEE does not become an owner of the software, source code, or related materials. This paragraph shall remain effective regardless of changes or modifications made by LICENSEE to the source code. LICENSOR's sole responsibilites are as follows: 1.0 - LICENSOR shall provide LICENSEE with an AS IS copy of source code to the above module(s) on a sealed diskette for version 3.00c of the software. 1.1 - Should the diskette prove to be defective, LICENSOR shall provide LICENSEE with another copy of the materials on a replacement diskette. LICENSEE's responsibilities are as follows: 2.0 - LICENSEE may make ONE copy of the source code contained on diskette for backup purposes. 2.1 - LICENSEE will not disclose, reveal, transmit, transport, copy, store in a retrieval system, print, or otherwise transport the source code in whole or in part (physically, electronically, digitally, mechanically, electromagnetically or otherwise) outside of the physical constraints of the office space of LICENSEE. 2.2 - LICENSEE will not alter, remove or obscure LICENSOR's copyright or trademark notices. 2.3 - Any changes to the source code by LICENSEE for production use will be conveyed to users/callers with the following statement in the do_logo() function: COMPILED CHANGES MADE UNDER LICENSE AGREEMENT WITH GILMORE SYSTEMS 2.4 - LICENSEE is responsible for obtaining a compiler suitable for compiling the supplied source code (ie: Microsoft C v6.00A). 2.5 - LICENSEE will make every effort to keep source code from being subject to theft, retrieval, or otherwise transported from the physical restraints of LICENSOR's office space. 2.6 - LICENSEE will not rent, lease, sub-license or otherwise transfer the source code. 2.7 - LICENSEE will not produce or compile 3rd-party or add-on programs for "MAGUUCP" compiled from any source code containing any of LICENSEE's provided source code (either in whole or in part). 2.8 - LICENSEE is not currently engaged in, and will not become engaged MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Distribution Rights & Source Code Licensing Page 7-4 in the business of writing, marketing, or otherwise distributing telecommunications software while this agreement is in effect. 2.9 - In the event LICENSEE becomes engaged in writing, marketing, or otherwise distributing telecommunications software, LICENSEE will notify LICENSOR in writing that it is terminating this agreement. LICENSEE must accompany the written notification with the original software diskette containing the source code, along with any changes made to the source code, and will immediately destroy any and all copies or partial copies of any source code obtained from LICENSEE. Furthermore, LICENSEE may not market, sell or otherwise distribute or release host telecommunications programs for a period of one year from the date of termination. 2.10- LICENSOR may offer distribution rights for any compiled changes to "MAGUUCP" for an additional fee. LICENSEE should contact LICENSOR to obtain a DISTRIBUTION RIGHTS agreement and current fee structure. GENERAL: 3.0 - Either party may terminate this agreement at any time by serving written communication upon the other party. Any termination requires LICENSEE to return to LICENSOR the the original software diskette containing the source code, along with any changes made to the source code, and LICENSEE will immediately destroy any and all copies or partial copies of any source code obtained from LICENSEE. Furthermore, LICENSEE may not market, sell or otherwise distribute or release any host telecommunications programs for a period of one year from the date of termination. 3.1 - LICENSOR shall not be held responsible for any damages (ie: loss of profit, machine or file system damage, loss of data, loss of time, or any other consequential or inconsequential damages) resulting from the use or misuse of supplied source code. 3.2 - This agreement shall be effective indefinitely or until written termination is served from one party to the other. 3.3 - LICENSEE may obtain a refund by returning the unopened, sealed diskette packaging within 3 days of receipt, accompanied by a written termination letter. 3.4 - No refund shall be made after 3 days of delivery to LICENSEE's office address. No refund shall be made if the sealed diskette packaging has been broken. 3.5 - Should any part of this agreement prove to be illegal or unenforceable by law, only that portion of the agreement shall become null and void but shall in no way effect the legality of the remaining terms, conditions and provisions of the agreement. 3.6 - This agreement shall be governed by California law. LICENSEE: _____________________________ DATE: ______________ LICENSOR: _____________________________ DATE: ______________ Gilmore Systems MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems Thank You Page 7-6 Thank you for using MAGUUCP communications software for OS/2. Your feedback about this program is welcome. Simply dial our BBS with it and leave us a message (or [C]omment to Sysop), or e-mail us: postmaster@gilmore.com MAGUUCP Communications for OS/2 - (C)Copyright 1989,1996 Gilmore Systems